The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!
From the Wiki University
What evidence can you provide to prove your understanding of each of the following citeria?
Code using advanced data structures
|
|
Design dynamic data structures Completed |
Evidence:
|
Implement and use dynamic data structures, including double-linked lists and binary trees for coding Completed |
Evidence:
|
Code using advanced algorithms
|
|
Code using hashing techniques Completed |
Evidence:
|
Consider and record, the advantages and disadvantages, of at least three sorting algorithms Completed |
Evidence:
|
Code at least one sorting algorithm Completed |
Evidence:
|
Code advanced searching techniques for use with complex data structures Completed |
Evidence:
|
Write a simple multi-process application
|
|
Use features of the language that enable inter-process communication through at least one mechanism Completed |
Evidence:
|
Use features of the language that allow for operating system ‘signals’ to be captured and responded to Completed |
Evidence:
|
Use third-party libraries
|
|
Use a third-party library in the construction of an application Completed |
Evidence:
|
Reference third-party documentation Completed |
Evidence:
|
Use procedural techniques to write an application, to work within a graphical user interface (GUI) environment Completed |
Evidence:
|
Debug the code
|
|
Use integrated development environment (IDE) debugging facilities, or a stand-alone debugger Completed |
Evidence:
|
Use program debugging techniques to detect, and resolve, errors of syntactical, logical and design origin Completed |
Evidence:
|
Document activities
|
|
Use source-code version control Completed |
Evidence:
|
Adhere to guidelines for developing maintainable code, and to a set of provided coding standards Completed |
Evidence:
|
Apply suitable internal documentation to all the code created, using the tools available in the target language Completed |
Evidence:
|
Test the code
|
|
Design and document the tests to be undertaken Completed |
Evidence:
|
Undertake limited testing of the produced code, to ensure that it complies with the program specification Completed |
Evidence:
|
Capture the test results Completed |
Evidence:
|
Create an application
|
|
Develop a solution, according to program-specification design document Completed |
Evidence:
|
Design the algorithm, and construct, and test, the application in response to a problem description and language Completed |
Evidence:
|